CVE-2022-50301
iommu/omap: Fix buffer overflow in debugfs
Description
In the Linux kernel, the following vulnerability has been resolved: iommu/omap: Fix buffer overflow in debugfs There are two issues here: 1) The "len" variable needs to be checked before the very first write. Otherwise if omap2_iommu_dump_ctx() with "bytes" less than 32 it is a buffer overflow. 2) The snprintf() function returns the number of bytes that *would* have been copied if there were enough space. But we want to know the number of bytes which were *actually* copied so use scnprintf() instead.
INFO
Published Date :
Sept. 15, 2025, 3:15 p.m.
Last Modified :
Dec. 4, 2025, 3:32 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Validate 'len' before the first write operation.
- Replace snprintf() with scnprintf() for correct byte counts.
- Apply the Linux kernel patch for iommu/omap.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-50301.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-50301 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-50301
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-50301 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-50301 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Dec. 04, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Added CWE CWE-787 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.0 up to (excluding) 6.0.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.10 up to (excluding) 4.14.296 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.15 up to (excluding) 4.19.262 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.220 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.150 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.75 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 3.19 up to (excluding) 4.9.331 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 5.19.17 Added Reference Type kernel.org: https://git.kernel.org/stable/c/0c7043a5b5c3b35f5dc8875757f71e7f491d64d4 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/184233a5202786b20220acd2d04ddf909ef18f29 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/2fee0dbfaeaaa4bda04279ce772c4572b1429d04 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/4010a1afaae1c0fb9c2cac5de703bed29b1f1782 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/648472df221f2bbffb433b964bcb87baccc586d8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/706e359cf046c142db290244c3f4938b20fbe805 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9814cc350e0765ce69244bf55ae4c8b29facd27e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/bd0438f534b2e31b12f0b39b355c5dc2bbdaf854 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ec53b99b6b9da8b501f001595a6260c03b42d5b7 Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 15, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: iommu/omap: Fix buffer overflow in debugfs There are two issues here: 1) The "len" variable needs to be checked before the very first write. Otherwise if omap2_iommu_dump_ctx() with "bytes" less than 32 it is a buffer overflow. 2) The snprintf() function returns the number of bytes that *would* have been copied if there were enough space. But we want to know the number of bytes which were *actually* copied so use scnprintf() instead. Added Reference https://git.kernel.org/stable/c/0c7043a5b5c3b35f5dc8875757f71e7f491d64d4 Added Reference https://git.kernel.org/stable/c/184233a5202786b20220acd2d04ddf909ef18f29 Added Reference https://git.kernel.org/stable/c/2fee0dbfaeaaa4bda04279ce772c4572b1429d04 Added Reference https://git.kernel.org/stable/c/4010a1afaae1c0fb9c2cac5de703bed29b1f1782 Added Reference https://git.kernel.org/stable/c/648472df221f2bbffb433b964bcb87baccc586d8 Added Reference https://git.kernel.org/stable/c/706e359cf046c142db290244c3f4938b20fbe805 Added Reference https://git.kernel.org/stable/c/9814cc350e0765ce69244bf55ae4c8b29facd27e Added Reference https://git.kernel.org/stable/c/bd0438f534b2e31b12f0b39b355c5dc2bbdaf854 Added Reference https://git.kernel.org/stable/c/ec53b99b6b9da8b501f001595a6260c03b42d5b7